home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr11
/
pdox693.zip
/
TI598.ASC
< prev
next >
Wrap
Text File
|
1993-05-12
|
9KB
|
331 lines
PRODUCT : Paradox NUMBER : 598
VERSION : 3.5 and Up
OS : DOS
DATE : May 12, 1993 PAGE : 1/5
TITLE : Connecting to VAX Rdb/VMS V4.0
Note that the procedures described in this document are usually
necessary to gain client/server access to an Rdb/VMS database,
using PARADOX SQL LINK. Also note that the VAX System Manager or
Cluster Manager is normally the person who coordinates and/or
performs these procedures. The System Manager or Cluster Manager
is someone who knows the VAX VMS operating system and is directly
responsible for the software configuration of the system. This
person is usually the person who makes changes to the system
software. It is not advisable to perform VAX VMS system
management functions without the advice/consent/or coordination
of a VAX System Manager or Cluster Manager. From this person,
you will need to request the following:
1) USERNAME ACCOUNT
Whenever PC users are first getting into client/server access in
using Rdb/VMS on a VAX, they will be going through a sign on VAX
signon procedure which is initiated in a PARADOX SQL LINK server
signon screen. To be able to sign in, a user must defined as a
user on the VAX server system. This means that each user who
signs on to the VAX will get a user account name, such as their
last name, and a password. Note that it is advisable for a
client/server user to do their first VAX signon on a VTxxx
terminal connected to the VAX system. Why? Two reasons, 1) they
will determine that they definitely have a VAX VMS username
account and 2) VAX VMS requires that each time a new user is
added to the system or a password is redefined by the System
Manager, the password must be changed by the affected user the
very first time they login after the new username definition or
password change. This password must be respected and treated
with care because it allows access to the system.
2) ACCESS TO REQUIRED SYSTEM AND DATABASE RESOURCES
ACLs (Access Control Lists) for VAX VMS and Rdb/VMS will probably
have to be defined also to permit access to the database
resources you need to connect to. ACLs are how security is
administered in the VAX VMS and the Rdb/VMS environment.
PRODUCT : Paradox NUMBER : 598
VERSION : 3.5 and Up
OS : DOS
DATE : May 12, 1993 PAGE : 2/5
TITLE : Connecting to VAX Rdb/VMS V4.0
3) MODIFICATION OF THE SQLSRV$PROXY.DAT FILE TO ADD USERS
See the steps outlined below (section titled "PROXY ACCESS")
WHEN USING PARADOX SQL LINK, MAKE SURE THE SQL SERVICES PROCESS
IS RUNNING
If an attempt is made to run PARADOX SQL LINK when the SQL
Services process is not presently running under VAX VMS, the user
will see this message, "Network Connection Error". This is a
signal to the user to get the SQL Services process started under
VAX VMS.
WHAT IS SQL SERVICES?
A Digital client/server software product that allows application
programs running on various types of computers to access DIGITAL
Standard Relational Interface (DRSI) compliant databases using
the dynamic interface to VAX SQL, an implementation of the
industry-standard SQL.
HOW TO CHECK TO SEE IF SQL SERVICES IS RUNNING ON THE VAX
Since using the PARADOX SQL LINK product requires that the SQL
Services process be currently running on the VAX node that you
plan to connect with, you will want to determine if this process
is running by typing this command on the VAX: $ SHOW SYSTEM.
This command will cause a list of every process which is
currently in running in the system. If a process named
SQL$SERVER is running, then that is the SQL Services process.
PRODUCT : Paradox NUMBER : 598
VERSION : 3.5 and Up
OS : DOS
DATE : May 12, 1993 PAGE : 3/5
TITLE : Connecting to VAX Rdb/VMS V4.0
STARTING THE SQL SERVICES PROCESS IF IT IS NOT CURRENTLY RUNNING
The DCL command procedure (SQLSRV$STARTUP.COM) which starts up
the SQL Services process is found under the SYS$STARTUP logical
directory name. Note that SYSPRIV privileges will probably be
required to execute this procedure. If you don't have SYSPRIV
privileges, get the VMS System Manager to perform this task for
you. To successfully start the SQL Services process, enter these
commands:
$ SET DEF SYS$STARTUP
$ @SQLSRV$STARTUP
The access methods for VAX Rdb/VMS V4.0 have been modified to
increase the performance of VAX SQL/Services. These methods are
provided in three modes:
1. Explicit
o Paradox 4.0 SQL Link is an Rdb 4.1 Client and
requires Explicit access through:
o DecNet or
o TCPIP
2. Default
3. Proxy.
o Paradox 3.5 (SQL Link 1.0) is a Rdb 3.1 Client and
Requires Proxy Access.
EXPLICIT ACCESS
When a VAX Rdb/VMS V4.0 client accesses a VAX Rdb/VMS V4.0
server, an explicit access method is used. To provide backward
PRODUCT : Paradox NUMBER : 598
VERSION : 3.5 and Up
OS : DOS
DATE : May 12, 1993 PAGE : 4/5
TITLE : Connecting to VAX Rdb/VMS V4.0
compatibility and reliable connections between VAX Rdb/VMS V3.1B
clients and VAX Rdb/VMS V4.0 servers, the proxy access method
must be used.
DEFAULT ACCESS
For non-secure systems, the default access method is provided for
both VAX Rdb/VMS 3.1B clients and VAX Rdb/VMS 4.0 clients. This
provides access to the SQLSRV$SRV default account if the default
account has been enabled on the server.
PROXY ACCESS
Because Paradox SQL Link V1.0 with Paradox 3.5 operates as a
Rdb/VMS 3.1B client, proxy access must be created to the Rdb 4.0
server.
Proxy access permits SQL Link to access the server when the node
name is specified in a sqlsrv_associate routine call and an entry
exists for the incoming application request in the
SQLSRV$PROXY.DAT file. The proxy file resides in the directory
defined by the logical, SYS$STARTUP, on the server system. What
needs to be defined in the SQLSRV$PROXY.DAT file on the server is
for all users from a node to have access to the server. This is
done by defining access as follows in the SQLSRV$PROXY.DAT file
on the VAX Rdb/VMS V4.0 Server system, using the following
syntax:
ADD/PROXY REMOTE_NODENAME::REMOTE_USERNAME LOCAL_USERNAME
An example of an actual SQLSRV$PROXY.DAT file under
SYS$STARTUP:
add/proxy bartls::slater_wb slater_wb
add/proxy bartls::kahn_p kahn_p
add/proxy bartls::reiss_s reiss_s
add/proxy bartls::koulouris_m koulouris_m
PRODUCT : Paradox NUMBER : 598
VERSION : 3.5 and Up
OS : DOS
DATE : May 12, 1993 PAGE : 5/5
TITLE : Connecting to VAX Rdb/VMS V4.0
add/proxy bartls::coffey_j coffey_j
add/proxy bartls::zenreich_a zenreich_a
add/proxy bartls::koski_t koski_t
add/proxy bartls::system system
This allows user LOCAL_USERNAME to access REMOTE_NODENAME under
the proxy of REMOTE_USERNAME.
To set up proxy access you must first shut down SQL/Services,
edit the SQLSRV$PROXY.DAT file as suggested above.
After the edit, use the SQLSRV$SHUTDOWN.COM file to shut down the
SQL$SERVICES process in the system. It is better to wait until
after hours to make sure no one will be using the SQL$SERVICES
process.
$ SET DEF SYS$STARTUP
$ @SQLSRV$SHUTDOWN
After the shutdown procedure is successful, use the
SQLSRV$STARTUP procedure to restart the SQL SERVICES process.
When SQL$SERVICES restarts, the new SQLSRV$PROXY.DAT parameters
will then take effect at that time.
$ SET DEF SYS$STARTUP
$ @SQLSRV$STARTUP
Note that both the SQLSRV$SHUTDOWN.COM and the SQLSRV$STARTUP.COM
files reside in the SYS$STARTUP logical directory on the VAX
server.
For additional information, please refer to your VAX Rdb/VMS V4.0
Accessing SQL/Services documentation.
DISCLAIMER: You have the right to use this technical information
subject to the terms of the No-Nonsense License Statement that
you received with the Borland product to which this information
pertains.